The Runtime Engine is the heart of the application on the server, performing all tasks related to the application with the exception of batched tasks (which are run, instead, by the Task Engine).
The Runtime Services settings provide some control over how requests are processed and handled. You can set them for the entire platform or for each Runtime Engine server in a multi-server deployment. By adjusting these settings per Runtime Engine instance, admins can better control performance and resource allocation. This is especially true when hardware is not identical across all runtime engines.
Note: In a multi-server deployment, each server will appear in the list going down the page (purple highlight below).
Admin Console Runtime Services
Settings
- General Track Timeout - The length of time that a general thread should wait to process a job before timing out.
- Fast Track Timeout - The length of time that a fast track/lane thread should wait to process a job before timing out.
- Request Default Network Timeout - The amount of time to wait for network requests. Increase this value on very slow networks. Note: If there is a timeout, the request goes back to client for a re-request sequence.
- Request Default Cache Timeout - The amount of time the response cache is held while waiting for repeat requests from the client on very slow networks. Increase this value on very slow networks.
- General Track Threads Number - The number of concurrent general threads that can be created in the Runtime Engine. Thread thrashing - over use of threads - may decrease performance, so do not set this to an excessively high value.
- Fast Track Threads Number - The number of concurrent fast track/lane threads that can be created in the Runtime Engine. Thread thrashing - over use of threads - may decrease performance, so do not set this to an excessively high value. Care should also be taken to not overwhelm data sources by excessively increasing the number of concurrent queries being launched from Pyramid.